test: qualify the migrated inference path - #39
Open
uermel wants to merge 4 commits into
Open
Conversation
This was referenced Aug 19, 2026
…validation # Conflicts: # src/copick_easymode/core/inference.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tracks #36 and is the third PR in the copick-easymode OME-Zarr 0.5 / Zarr v3 migration stack.
This completes the source-side validation path:
The prior local CPU record was removed because its probability map produced an all-background segmentation and its committed schema had been edited by hand. Replacement evidence should be committed only after the corrected command succeeds unchanged on a real input that produces foreground.
Validation: all 40 source tests pass across the configured matrix, and all existing CI checks are green.
Remote S3/SSH/ML Croissant fault-injection evidence remains environment-owned and is documented rather than claimed as automated. No PyPI setup, release PR, or publication is included.